• 专利附录
  • 专利说明
  • 权利要求
  • 类似技术
  • 同族专利
  • 引用文献
  • 法律状态
  • 优先权
    • 专利摘要:
    The present invention provides a method for managing configuration changes in a network where data processing systems, particularly software products 250, must be distributed to client workstations. The method provides a definition of reference models 220e-220d, which consist of trees 215, where each reference model is a software product and / or hardware feature and a corresponding client workstation (subscriber). Components, such as their required target state). The target configuration 230 of the client workstation associated with each reference model is determined by inheriting the components of the parent reference models. The list 245 of operations to be performed on each client workstation to reach the corresponding target configuration is determined by comparing the target configuration with the current configuration of the client workstations stored in the corresponding inventory 245.
    公开号:KR20030090680A
    申请号:KR10-2003-7012194
    申请日:2002-03-05
    公开日:2003-11-28
    发明作者:마리넬리클라우디오；피체티루이기
    申请人:인터내셔널 비지네스 머신즈 코포레이션；
    IPC主号:
    专利说明:

    Configuration change management method and data processing system {A METHOD AND SYSTEM FOR MANAGING CONFIGURATION CHANGES IN A DATA PROCESSING SYSTEM}
    [1] The present invention provides a method for managing configuration changes in a data processing system having a plurality of destination units, which is a tree starting from a root reference model. Providing a plurality of constructed reference models, associating each destination unit with a reference model that includes configuration information specific to this destination unit, and configuration information of the reference models in the path from the root reference model to the selected reference model. And determining a target configuration for the destination unit associated with the selected reference model, and causing each destination unit associated with the selected reference model to be updated according to the target configuration.
    [2] The present invention also provides a computer program for performing this method, a product storing the program, and a corresponding data processing system.
    [3] Other features and advantages of the method according to the present invention will become apparent by reading the following description of the preferred embodiments of the present invention with reference to the accompanying drawings, which are intended to be illustrative rather than limiting of the invention. will be.
    [4] 1 is a basic block diagram of a networking system in which the method of the present invention may be used;
    [5] 2 is a diagram of a partial content of working memory of a server workstation included in a networking system, FIG.
    [6] 3A and 3B are flow diagrams of a method of managing configuration changes at a client workstation of a networking system.
    [7] 1 illustrates a networking system 100 such as a wide area network (WAN) used in a large enterprise. Networking system 100 is typically formed by a number of workstations 105 that are comprised of PCs (personal computers). Workstation 105 is clustered around corresponding concentrators 110, such as routers / hubs, and concentrator 110 is installed in a distributed location and accessible by telephone line 115 Do. Networking system 100 has a client / server architecture, where one or more workstations 105 (usually comprised of powerful computers) manage network resources, such as shared files and devices, and other workstations 105 It acts as a client, where the end user runs the application according to server resources.
    [8] Each workstation 105 includes several units connected in parallel to a communication bus 120. In particular, the central processing unit (CPU) 125 controls the operation of the workstation 105, the working memory 130 (typically DRAM) is used directly by the CPU 125, and the ROM 135 Stores a basic program for starting workstation 105. Various peripheral units are connected to the bus 120 by respective interfaces. In particular, the bulk memory consists of a driver unit (DRV) 145 for reading the hard disk 140 and the CD ROM 150, and the workstation 105 comprises an input unit (IN) consisting of a keyboard and a mouse, for example. And an output unit (OUT) 160 composed of, for example, a monitor. Network interface card (NIC) 165 is used to connect workstation 105 to concentrator 110.
    [9] When a networking system is associated with a department or any other group in a company, when the networking system has a different topology, when the networking system is configured as a local area network (LAN), the networking system is a different component, such as one or more switches. Is similar to the foregoing, even if each workstation has a different structure, such as having a multiprocessor architecture.
    [10] 2 shows a partial content of the working memory 130 of a workstation operating as a software distribution server, where information (program and data) is typically stored on a hard disk and the program being operated by an operating system. And at least partially loaded into working memory 130 when it is operating with other application programs (not shown). The program is initially installed from the CD-ROM on the hard disk of the server workstation.
    [11] The working memory 130 includes an input / output interface (I / O) 205 for exchanging information with peripheral units of the server workstation. The input / output interface 205 is in communication with a configuration change management module (CONFIG) 210.
    [12] The configuration module 210 manages a repository of reference models (MODELS) 215, each defining a profile with configuration information specific for the corresponding client workstation. In the contemplated embodiment, the repository 215 includes an enterprise model 220e, a secretary model 220s, an administrator model 220m, a developer model 22Od. The configuration module 215 accesses the enterprise database 225.
    [13] A generic reference model contains one or more records that define each component. Each record consists of a field ELE that identifies a component, such as a software product or hardware feature. Field TGT refers to the required target state of a component, for example a target state for a software product indicates that the software product will be installed, removed, or installed / removed in a way that can be restored to its original state, and the target state for a hardware feature. Displays the hard disk size, CPU model or working memory capacity. Other field DPDs contain dependency information indicating the logical relationship between the components, such as field DPDs, which are required components (prerequisites) to operate the software product, and components that conflict with the software product (non-mandatory elements: ex -requisites) or components (co-requisites) that will be installed in a certain order with the software product.
    [14] The reference model further includes a field SBS that is used to associate this reference model with one or more client workstations (subscribers), the association step being performed statically and / or dynamically. When the subscriber is statically defined, the field SBS contains only a list of client workstations, and conversely, when the subscriber is dynamically defined, the field SBS is a query to run on the enterprise database 225. And the result of the query provides a list of client workstations.
    [15] Reference models are organized hierarchically in trees. In particular, the business model 220e defines the root of the tree, the secret model 220s and the manager model 220m depend on the business model 220e and the developer model 220d depends on the manager model 220m. do. As will be described in detail below, each child reference model 220s, 220m, 220d, each dependent on its corresponding parent reference model, is a root reference model 220e. Inherits the configuration information of all reference models in the path from) to the child reference model. This inheritance mechanism does not implement the "is-a" semantic form, for example, the developer is not a manager, but not all components of the manager model (but not subscribers). Is inherited by the developer model 220d.
    [16] The corporate database 225 defines an organizational chart of the enterprise and is composed of a relational table formed by records for each employee. The record consists of a field INFO containing information about the employee, such as the employee's name, telephone number, fax number, e-mail address, department, location, manager, and subordinates, if any. The field WS identifies, for example, the client workstation assigned to the employee, such as its type, serial number, location, IP address. The flag EX indicates that the client workstation assigned to the employee will be excluded from the result of the query (when asserted).
    [17] The configuration module 210 creates a memory structure 230 that represents the target configuration for the client workstation associated with the selected reference model. The target configuration 230 includes one or more components, each component being defined by respective fields ELE and TGT (each indicating the component and its target status), the target component 230 being a selected reference. Contains a list of client workstations associated with the model, each client workstation identified by a respective field WS.
    [18] The target configuration 230 is supplied to a synchronization engine (SYNC) 235, which accesses an inventory 240 that stores the current configuration of the client workstation. The configuration inventory 240 contains a record for each client workstation, where the record represents each field WS (identifying the client workstation) and the hardware features of the client workstation and the software product installed thereon. It consists of CURR. The synchronization engine 235 further accesses the state transition table 243. State transition table 243 consists of a lookup table, where each record has a key formed by fields STSs and STSes, where fields STSs and STSes belong to a general configuration belonging to a corresponding range (such as a hardware feature or software product). Indicate the start and end states of an element, respectively. The keys STSs and STSe are the operations that will be performed to reach the termination state STSe from the start state STSs (eg, install the software product, uninstall the software product, update the CPU, increase the size of the hard disk, and so on). It is associated with an attribute consisting of a field ACT to display.
    [19] The synchronization engine 235 creates a memory structure 245 that defines a list of operations to be performed on each client workstation associated with the selected reference model to reach the target configuration. In particular, the action list 245 includes a series of records, each of which has a field WS identifying the client workstation, a field ELE identifying the relevant component, a field indicating the corresponding action to be performed on the client workstation. It consists of ACT.
    [20] Action list 245 is provided to a deployment agent (DPEL) 250, which accesses a repository of software products (SW) 255. The deployment agent 250 builds a distribution package (PCK) 260 for each client workstation, which operates with one or more files containing software products to be installed on the client workstation. Instructions that automatically execute the operations (relative to the software product) indicated in the corresponding record of the list 245 (eg, installing or removing other software products included in the package). Deployment agent 250 controls the updating of information stored in configuration inventory 240.
    [21] The distribution package 260 is provided to a network interface (NET) 265, which transmits the package to the corresponding client workstation in accordance with the schedule scheduled by the deployment agent 250. The network interface is also directly connected to deployment agent 250 to supply messages received from client workstations. The synchronization engine 235 and the deployment agent 250 communicate with the configuration module 210 to provide return codes that receive the command and indicate the result of the corresponding operation.
    [22] Dummy models where the program and data are structured in different ways, when different modules or functions are provided, when the tree consists of a different number of reference models, and one or more reference models do not have any subscribers associated with them. ) Is similar to that described above, even if the enterprise database has a different architecture and stores different information, even if two or more client workstations are assigned to several employees. Alternatively, equivalent configuration information is included in the reference model, and different components (such as application parameters, databases, audio and video recordings or any other digitally encoded product) can be managed, ( For example, different target states are supported, indicating that a software product is present in a simple disabled state but should not be removed, or a subscriber may be associated with, for example, a profile or software application associated with each user logging in to a client workstation. Such as) different destination units.
    [23] As shown in Figures 3A and 3B, the entire software distribution application consists of configuration modules and performs the method 300 when the synchronization engine and the deployment agent operate on the server workstation. The method 300 begins at block 303 and then proceeds to block 306 where a menu with a set of possible choices is displayed to the system administrator on the monitor of the server workstation. This method executes an operation corresponding to the selection selected by the administrator. In particular, if the administrator has selected the Edit Reference Model Repository function, blocks 309-318 are performed, and if the administrator has selected the function to use the new configuration on the corresponding client workstation, blocks 320-375. If the administrator has opted to exit the software distribution application, then the method ends at final block 378.
    [24] At block 309 (edit function), the administrator removes the selected reference model (to reconstruct the tree) and inserts a new reference model into the tree or chooses to update the reference model. The method proceeds to block 312 where the administrator removes the component and creates a new component or updates the target state of the selected component if the reference model update is selected. Proceed to block 315, where the administrator can add dependencies information (pre-requisites, ex-requisites, common prerequisites, etc.) of selected components, such as to add, update, or remove items. (co-requisites)). At block 318, the administrator modifies the subscriber assigned to the selected reference model, in particular the identifier of the client workstation is removed from the corresponding list and the identifier of the new client workstation is inserted or the list of client workstations is dynamically modified. Queries defined by are created or updated. The method then returns to block 306 to wait for a new command by the manager.
    [25] At block 320 (deployment function), the manager selects one of the reference models to be executed. The method proceeds to block 321 where all components of the root reference model are added to the target configuration (empty at start up). The configuration module then checks whether a reference model selected at block 324 has been reached (and has been fully processed). If so, the method proceeds to block 325 (to be described below). If the selected reference model has not been reached, the method proceeds to block 330 where a new component of the reference model along the tree along the path from the root reference model to the selected reference model is considered (this new component is Starting with the first component in the child reference model that directly depends on the root reference model). If the target configuration does not include the current component, the method proceeds to block 333 where the current component is added to the target component, if the target configuration includes the current component, The method proceeds to block 336 where the dependency information and target status of the (previous) component in the target configuration are replaced with corresponding fields of the current component. In both cases, the method proceeds to block 324 to process the next component of the same reference model or the first component of the next reference model.
    [26] At block 325, the target configuration is updated according to the corresponding dependency information to resolve all logical relationships between the components. For example, components corresponding to prerequisite products and jointly essential products are added, which components are reconfigured to satisfy the order of installation requirements, and components corresponding to non-essential products to be removed are inserted.
    [27] The method then proceeds to block 338 where the configuration module verifies whether the subscriber is statically or dynamically defined in the selected reference model. If statically defined, the list of client workstations included in the selected reference model is added to the target configuration at block 339, and then the method proceeds to block 342 (to be described below). In contrast, if the subscription is dynamically defined, the corresponding queries included in the selected reference model are run on the enterprise database at block 345, thereby extracting a list of client workstations. This list is removed at block 348 of the client workstation to be excluded from the deployment of the new component in accordance with the corresponding flag. The method then proceeds to block 342.
    [28] In block 342, the current configuration of the client workstation associated with the selected reference model is extracted from the configuration inventory. The synchronization engine then generates an action list for each client workstation by comparing the target configuration with the current configuration corresponding thereto at block 351. In particular, if the current state of each component (software product or hardware feature) satisfies the desired target state, no action is performed, and vice versa, from the current state of the component to the target state of the component. The actions needed to arrive are extracted from the state transition table and added to the action list.
    [29] The method then proceeds to block 354, where the deployment agent verifies that the current hardware structure of the client workstation associated with the selected reference model meets the hardware prerequisites of the target configuration. For every client workstation that meets the hardware prerequisites of the target configuration, a corresponding deployment package is built at block 357, more specifically, inserting each software product into which the deployment agent will be installed into the deployment package. And add instructions to perform the required action. In the opposite case, for all client workstations that do not meet the hardware prerequisites of the target configuration, for example, because the CPU model fails to operate the software product to be installed or the hard disk size is insufficient, the error condition is blocked ( 366, in particular a warning message is provided to the administrator and the use of the target configuration to the client workstation is stopped.
    [30] In both cases, the method proceeds to block 372, where the package, if present, is sent over each network to each client workstation. Each package is received on a client workstation and the instructions contained within it are executed to install or uninstall the corresponding software product. A return code message is sent from each client workstation to the server workstation to report the result of the configuration change, whereby the deployment agent updates the configuration inventory at block 375. The method then proceeds to block 306 waiting for a new command by the administrator.
    [31] The following table specifies examples of components that belong to each reference model.
    [32]
    [33]
    [34] Here, suppose you want to run the developer model. The target configuration for client workstations associated with this developer model is defined as follows.
    [35]
    [36] Thus, if the client workstation associated with the developer model has only antivirus software products installed on it and its working memory size is larger than 128 MB, the following action list will be performed to reach the target configuration.
    [37]
    [38] For example, where a reporting function is provided, even if an enterprise inventory is stored at some place and an equivalent method is performed, such as when the queries are operated by other workstations, they are similar.
    [39] More generally, the present invention provides a method for managing configuration changes in a data processing system having multiple destination units. The method includes providing a plurality of reference models consisting of a tree starting from a root reference model, and associating each destination unit with a reference model that includes configuration information specific to that destination unit. Determining a target configuration for the destination unit associated with the selected reference model according to the configuration information of the reference models in the path from the root reference model to the selected reference model, wherein each destination unit associated with the selected reference model is updated according to the target configuration It further comprises the step of.
    [40] The method provides a scalable and flexible way of specifying the target configuration of each destination unit. In particular, the reference model allows each destination unit to be organized into logical and functional groups, depending on the role each destination unit plays in the system. As such, any profile or configuration change can be automatically reflected on the associated destination unit by simply modifying the corresponding reference model. In this way, a large system with a very large number of destination units can be managed like a small system by treating all the destination units associated with each reference model as a single group.
    [41] The hierarchical structure of the reference model greatly simplifies modeling of the destination unit by enabling a step-by-step definition of the target configuration of each destination unit. In fact, the components common to all destination units are: Only specified in the root reference model, components specific to each functional group are defined as they move along the tree. In this way, the number of reference models required to describe the entire system is greatly reduced and each change to the reference model is automatically reflected in the target configuration of all destination units associated with its child reference model.
    [42] The method according to the invention simplifies the use of the new configuration in the system. This makes the process of managing frequent configuration changes for different groups of destination units more reliable.
    [43] The preferred embodiment of the present invention described above provides other advantages. For example, the proposed algorithm is particularly simple and effective for determining the target configuration from the corresponding reference model that exists along the path from the root reference model to the selected reference model. This approach allows any reference model to inherit all the components of the parent reference model, while at the same time each reference model can override the target state or block the installation / uninstallation of any components specified in the parent reference model. Can be.
    [44] Alternatively, the target configuration can be determined in different ways, such as without the possibility of ignoring and / or blocking the components defined in the parent reference model.
    [45] Dependency information embedded in the reference model prevents the specification and implementation of incorrect configurations. In addition, by verifying the current hardware structure of each destination unit (to check whether the current hardware structure of each destination unit meets the hardware prerequisites of the target configuration), all software products to which each destination unit will be installed will behave correctly. It is guaranteed to exist at the level that makes it possible.
    [46] If the dependency information is used in different ways to determine the target configuration, the method may not be able to modify the target configuration, but simply enter an error state if the result of the verification is negative. In cases where only compatibility is demonstrated, if the dependency information is not specified in the reference model but is defined in the individual memory structure accessed by the configuration module each time the reference model is to be executed, then the package (even if an error state is entered) In any case, the case is similar to that described above, even when sent to the client workstation. However, the method according to the present invention may be performed on its own without the possibility of defining any dependency information for any hardware feature in the component or reference model.
    [47] The dynamic specification of the subscribers associated with each reference model allows you to evaluate the destination unit that should undergo configuration change execution when the new configuration is actually used. In addition, due to the possibility of excluding some destination units from the result of the queries, the destination units may temporarily remain unchanged without modifying the fields defining the subscribers in the corresponding reference model.
    [48] Alternatively, a destination unit can be associated with each reference model in a different way, e.g., defining a group of destination units (such as client workstations attached to a specific router), and the overall result of the query does not exclude any destination unit. Can be used at any time, and subscribers can only be defined dynamically or statically.
    [49] The inventory storing the current configuration of each destination unit allows the level of components present on the client workstation to be sufficiently tracked. For example, an administrator can choose to deploy a new software product that is already installed on a subset of client workstations and will now be installed on all client workstations of the system, or a new version of a software product already installed on a subset of client workstations. You can easily decide where to deploy.
    [50] The method described above is particularly advantageous for software distribution applications used in large networks, where new configurations are automatically deployed from server workstations to multiple client workstations.
    [51] If the state transition table is replaced by an equivalent memory structure, even if the action list is determined in a different way by comparing the target configuration with the current configuration of each destination unit (e.g. with an algorithm contained within the synchronization engine), similar. However, the proposed method can be implemented on its own without any configuration inventory (e.g., by dynamically collecting information by the server workstation indicating the current configuration of each client workstation) and the method of the present invention (even It can be used in different data processing systems that have destination units not connected to each other in the network, for example copying packages onto a manually distributed CD ROM, and can also be used in data processing systems that only control the hardware configuration.
    [52] Advantageously, the method of the present invention is implemented with a computer program provided on a CD ROM.
    [53] In contrast, a program may be provided on a floppy disk and preloaded on a hard disk or stored on any other computer readable medium to be transmitted to a computer via a network and directly loaded into the working memory of the computer. It may be provided or broadcasted more generally. However, the method according to the invention can also be carried out with a hardware structure installed on a server workstation, for example integrated in a semiconductor chip.
    [54] In order to satisfy the local and specific requirements, those skilled in the art can make numerous modifications and changes to the above-described method which fall within the protection scope of the present invention as defined in the following claims.
    权利要求:
    Claims (11)
    [1" claim-type="Currently amended] A method 300 of managing configuration changes in a data processing system having a plurality of destination units, the method comprising:
    Providing (309-318) a plurality of reference models consisting of trees starting from a root reference model,
    Associating each destination unit with a reference model comprising configuration information specified for the corresponding destination unit (338,339,345-348);
    Determining a target configuration (320-336) for a destination unit associated with the selected reference model according to configuration information of reference models in a path from the root reference model to a selected reference model;
    Causing each destination unit associated with the selected reference model to be updated according to the target configuration (342-375).
    How configuration management is managed.
    [2" claim-type="Currently amended] The method of claim 1,
    The configuration information includes at least one record indicating a target state of a corresponding component,
    Determining the target configuration (320-336), for each of the current record of the reference model that exists along the path,
    Verifying (330) that the target configuration includes a previous record for a component of the current record;
    Adding (333) the current record to the target configuration if the verification result is negative; and replacing (336) the target state of the previous record with the target state of the current record if the verification result is positive. doing
    How configuration management is managed.
    [3" claim-type="Currently amended] The method of claim 2,
    Providing dependency information 315 indicating a logical relationship between the components,
    The target configuration is further determined according to the dependency information of the corresponding component (325)
    How configuration management is managed.
    [4" claim-type="Currently amended] The method according to any one of claims 1 to 3,
    The configuration information includes an indication of at least one hardware prerequisite,
    The method is
    Further comprising verifying (351-360) whether the current hardware structure of each destination unit associated with the selected reference model satisfies each hardware prerequisite of the target configuration.
    How configuration management is managed.
    [5" claim-type="Currently amended] The method according to any one of claims 1 to 4,
    Executing a query on a memory structure to dynamically extract a list of destination units associated with the selected reference model (345).
    How configuration management is managed.
    [6" claim-type="Currently amended] The method of claim 5,
    And 348 excluding each destination unit from the list if a corresponding flag in the memory structure is asserted.
    How configuration management is managed.
    [7" claim-type="Currently amended] The method according to any one of claims 1 to 6,
    Providing an inventory (342) storing an indication of the current configuration of each destination unit,
    Determining (351) an action list for reaching the target configuration on each destination unit associated with the selected reference model according to a comparison result between the target configuration and the corresponding current configuration.
    How configuration management is managed.
    [8" claim-type="Currently amended] The method of claim 7, wherein
    The configuration information includes indications of at least one digitally encoded product to be installed or removed,
    The data processing system consists of a server workstation and a network each having a plurality of client workstations associated with at least one destination unit,
    The method includes, for each destination unit associated with the selected reference model,
    Building (357) a package under the control of the server workstation, the package including instructions for automatically executing each product of the target configuration to be installed and the action list;
    Distributing (372) the package over the network to the client workstation associated with the destination unit;
    Updating (375) the inventory in accordance with an operation executed on the client workstation.
    How configuration management is managed.
    [9" claim-type="Currently amended] A computer program (210,235,250) which is directly loadable into a working memory (130) of a computer (105) and which, when executed on the computer, performs the method according to any one of the preceding claims.
    [10" claim-type="Currently amended] A program product (150) comprising a computer readable medium on which the program (210, 235, 250) of claim 9 is stored.
    [11" claim-type="Currently amended] In the data processing system 100,
    Multiple destination units 105,
    Means for providing a plurality of reference models consisting of a tree starting from the root reference model (205-215),
    Means (210, 215, 225, 230) for associating each destination unit with a reference model that includes configuration information specified for the corresponding destination unit;
    Means (230-245) for determining a target configuration for a destination unit associated with the selected reference model in accordance with configuration information of the reference models in the path from the root reference model to a selected reference model;
    Means (245-265) for causing each destination unit associated with the selected reference model to be updated in accordance with the target configuration.
    Data processing system.
    类似技术:
    公开号 | 公开日 | 专利标题
    US9870218B2|2018-01-16|Methods and systems for upgrading and installing application packages to an application platform
    US10430204B2|2019-10-01|System and method for cloud provisioning and application deployment
    US9594778B1|2017-03-14|Dynamic content systems and methods
    JP6313838B2|2018-04-18|Specifying user interface elements
    US9703890B2|2017-07-11|Method and system that determine whether or not two graph-like representations of two systems describe equivalent systems
    US20160357541A1|2016-12-08|Systems and Methods for Managing Distributed Applications
    US8671084B2|2014-03-11|Updating a data warehouse schema based on changes in an observation model
    US8494996B2|2013-07-23|Creation and revision of network object graph topology for a network performance management system
    EP2140370B1|2018-12-05|Unified service management
    JP5394123B2|2014-01-22|Multiple device management method and system
    TWI412995B|2013-10-21|On-demand database service system, method, and computer program product for verifying that a developed application will operate properly with at least one other application
    US5557793A|1996-09-17|In an object oriented repository, a method for treating a group of objects as a single object during execution of an operation
    JP3670965B2|2005-07-13|Client / server system for maintaining application preferences in a hierarchical data structure according to user and user group or terminal and terminal group context
    Hallerbach et al.2010|Configuration and management of process variants
    US6871223B2|2005-03-22|System and method for agent reporting in to server
    US6061726A|2000-05-09|Dynamic rights assignment apparatus and method using network directory services
    US8706879B2|2014-04-22|Automated discovery and inventory of nodes within an autonomic distributed computing system
    US6253240B1|2001-06-26|Method for producing a coherent view of storage network by a storage network manager using data storage device configuration obtained from data storage devices
    US6038586A|2000-03-14|Automated software updating and distribution
    US7340491B2|2008-03-04|Methods and apparatus for data preservation and software distribution within an enterprise system
    US8515799B2|2013-08-20|Constructing change plans from component interactions
    CA2574589C|2015-03-17|Apparatus, system and method for automatically discovering and grouping resources used by a business process
    JP4210155B2|2009-01-14|Monitoring system, method and computer program for remotely monitoring devices
    JP5147840B2|2013-02-20|Declarative Management Framework |
    US8250570B2|2012-08-21|Automated provisioning framework for internet site servers
    同族专利:
    公开号 | 公开日
    WO2002086696A3|2003-10-16|
    AT400938T|2008-07-15|
    EP1380134A2|2004-01-14|
    KR100550758B1|2006-02-08|
    GB0109618D0|2001-06-06|
    WO2002086696A2|2002-10-31|
    US20040153869A1|2004-08-05|
    AU2002257717A1|2002-11-05|
    EP1380134B1|2008-07-09|
    CA2442559A1|2002-10-31|
    US7370323B2|2008-05-06|
    US8099728B2|2012-01-17|
    JP2004536381A|2004-12-02|
    DE60227496D1|2008-08-21|
    GB2374687A|2002-10-23|
    US20080215558A1|2008-09-04|
    引用文献:
    公开号 | 申请日 | 公开日 | 申请人 | 专利标题
    法律状态:
    2001-04-19|Priority to GB0109618A
    2001-04-19|Priority to GB0109618.9
    2002-03-05|Application filed by 인터내셔널 비지네스 머신즈 코포레이션
    2002-03-05|Priority to PCT/EP2002/003363
    2003-11-28|Publication of KR20030090680A
    2006-02-08|Application granted
    2006-02-08|Publication of KR100550758B1
    优先权:
    申请号 | 申请日 | 专利标题
    GB0109618A|GB2374687A|2001-04-19|2001-04-19|Managing configuration changes in a data processing system|
    GB0109618.9|2001-04-19|
    PCT/EP2002/003363|WO2002086696A2|2001-04-19|2002-03-05|A method and system for managing configuration changes in a data processing system|
    [返回顶部]